DEV: always change postgres permissions on existing data directory #973
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If permissions of the initial data directory get changed, the install script is unable to reset the permissions to the expected user. The intent of the chown command is to ensure the permissions of the database and run directory are consistent and known. This allows it to do that on an existing data directory where this is more likely to occur. This uses a more consistent find command by moving chown command under exec Do not rely on a file glob which can error on too many files.
|
This is great. I've had to do this several times myself on upgrades from a very old container and have helped several people do it on meta. Thanks! |
tgxworld
approved these changes
Jul 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If permissions of the initial data directory get changed, the install script is unable to reset the permissions to the expected user.
The intent of the chown command is to ensure the permissions of the database and run directory are consistent and known. This allows it to do that on an existing data directory where this is more likely to occur.
This uses a more consistent find command by moving chown command under exec Do not rely on a file glob which can error on too many files.